Data processing methods, apparatuses, and terminal devices

ABSTRACT

A computer-implemented method includes providing, by one or more processing devices, a service code management interface; receiving, by the one or more processing devices, a specified quantity that is input by a user in the service code management interface; generating, by the one or more processing devices, the specified quantity of service codes, wherein the specified quantity of service codes comprise the same user identification information; and displaying, by the one or more processing devices, the specified quantity of service codes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of PCT Application No.PCT/CN2019/094875, filed on Jul. 5, 2019, which claims priority toChinese Patent Application No. 201810839423.0, filed on Jul. 27, 2018,and each application is hereby incorporated by reference in itsentirety.

TECHNICAL FIELD

Embodiments of the present specification relate to the field of computertechnologies, and in particular, to data processing methods,apparatuses, and terminal devices.

BACKGROUND

With the continuous development of mobile payment technologies, mobilepayment is gradually changing people's daily travel modes. More publictransportation is beginning to support mobile payment. Users can usetwo-dimensional codes generated by mobile terminals to take publictransportation. Specifically, when taking public transportation, a usercan use a mobile terminal to generate a two-dimensional code, scan thecode at an entry station, and scan the code at an exit station, therebycompleting the payment. In related technologies, a mobile terminal cangenerate only one two-dimensional code each time for one user to takepublic transportation. As such, when multiple persons traveling togethertake public transportation and one of them makes payment, the userusually needs to perform the operation multiple times so that the mobileterminal generates multiple two-dimensional codes. Consequently, useroperations are cumbersome and user experience is poor.

SUMMARY

A purpose of embodiments of the present specification is to provide dataprocessing methods, apparatuses, and terminal devices, so as to simplifyuser operations and improve user experience.

To achieve the previous purpose, some embodiments of the presentspecification provide a data processing method, including the following:providing a service code management interface; receiving a specifiedquantity that is input by a user in the service code managementinterface; generating the specified quantity of service codes, where thespecified quantity of service codes include the same user identificationinformation; and displaying the specified quantity of service codes.

To achieve the previous purpose, some embodiments of the presentspecification provide a data processing apparatus, including thefollowing: a providing unit, configured to provide a service codemanagement interface; a receiving unit, configured to receive aspecified quantity that is input by a user in the service codemanagement interface; a generating unit, configured to generate thespecified quantity of service codes, where the specified quantity ofservice codes include the same user identification information; and adisplaying unit, configured to display the specified quantity of servicecodes.

To achieve the previous purpose, some embodiments of the presentspecification provide a terminal device, including the following: adisplaying component, configured to display a service code managementinterface and a service code; and a processor, coupled to the displayingcomponent, and configured to: control the displaying component todisplay the service code management interface; receive a specifiedquantity that is input by a user in the service code managementinterface; generate the specified quantity of service codes, where thespecified quantity of service codes include the same user identificationinformation; and control the displaying component to display thespecified quantity of service codes.

It can be seen from the technical solutions provided in the previousembodiments of the present specification that, in some embodiments ofthe present specification, the mobile terminal can provide the servicecode management interface; can receive the specified quantity that isinput by the user in the service code management interface; can generatethe specified quantity of service codes, where the specified quantity ofservice codes include the same user identification information; and candisplay the specified quantity of service codes. As such, when multiplepersons traveling together take public transportation and one of themmakes payment, the user performs the operation once so that the mobileterminal generates multiple service codes, thereby simplifying useroperations and improving user experience.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in some embodiments of the presentspecification or in the existing technology more clearly, the followingbriefly describes the accompanying drawings needed for describing someembodiments or the existing technology. Clearly, the accompanyingdrawings in the following descriptions merely show some embodiments ofthe present specification, and a person of ordinary skill in the art canstill derive other drawings from these accompanying drawings withoutcreative efforts.

FIG. 1 is a flowchart illustrating a data processing method, accordingto some embodiments of the present specification;

FIG. 2 is a schematic diagram illustrating a functional structure of adata processing apparatus, according to some embodiments of the presentspecification;

FIG. 3 is a schematic diagram illustrating a functional structure of aterminal device, according to some embodiments of the presentspecification;

FIG. 4 is a schematic diagram illustrating an electronic metro card,according to some embodiments of the present specification;

FIG. 5 is a schematic diagram illustrating a service code managementinterface, according to some embodiments of the present specification;

FIG. 6 is a schematic diagram illustrating a service code displayinterface, according to some embodiments of the present specification;

FIG. 7 is a schematic diagram illustrating a label, according to someembodiments of the present specification; and

FIG. 8 is a schematic diagram illustrating an enlarged displayinterface, according to some embodiments of the present specification.

DESCRIPTION OF EMBODIMENTS

The following clearly describes the technical solutions in someembodiments of the present specification with reference to theaccompanying drawings in some embodiments of the present specification.Clearly, the described embodiments are merely some but not all of someembodiments of the present specification. All other embodiments obtainedby a person of ordinary skill in the art based on some embodiments ofthe present specification without creative efforts shall fall within theprotection scope of the present specification.

Some embodiments of the present specification provide a data processingsystem. The data processing system can implement a public transportationcharging service. For example, the public transportation correspondingto the public transportation charging service can be a metro, a bus, atram, a high-speed railway, etc. Specifically, the public transportationcharging service can be a segmented charging service or a one ticketprice charging service.

In some embodiments, the data processing system can include a mobileterminal. The mobile terminal can have a service code generationfunction. A service code can include a graphical code, and the graphicalcode can include a bar code, a two-dimensional code, etc. The mobileterminal can be implemented in a form of hardware or software, or can beimplemented in a form of a combination of hardware and software. Forexample, the mobile terminal can be a hardware device such as asmartphone, a tablet electronic device, a portable computer, a personaldigital assistant (PDA), or a smart wearable device. The mobile terminalcan also be an application program running on the hardware device.

In some embodiments, the data processing system can further include astation-entry toll terminal. The station-entry toll terminal can have aservice code scanning and recognition function. The station-entry tollterminal can be implemented in a form of hardware or software, or can beimplemented in a form of a combination of hardware and software. Forexample, the station-entry toll terminal can be a hardware device suchas a smartphone, a tablet electronic device, a portable computer, apersonal digital assistant (PDA), an in-vehicle device, a POS machine(such as a merchant POS machine, a bus POS machine, or a metro POSmachine), or a smart self-service terminal (kiosk) (such as a metroticket vending machine or a train ticket vending machine). Thestation-entry toll terminal can also be an application program runningon the hardware device.

In some embodiments, the data processing system can further include astation-exit toll terminal. The station-exit toll terminal can have aservice code scanning and recognition function. The station-exit tollterminal can be implemented in a form of hardware or software, or can beimplemented in a form of a combination of hardware and software. Forexample, the station-exit toll terminal can be a hardware device such asa smartphone, a tablet electronic device, a portable computer, apersonal digital assistant (PDA), an in-vehicle device, a POS machine(such as a merchant POS machine, a bus POS machine, or a metro POSmachine), or a smart self-service terminal (kiosk) (such as a metroticket vending machine or a train ticket vending machine). Thestation-exit toll terminal can also be an application program running onthe hardware device. It is worthwhile to note that, the station-exittoll terminal and the station-entry toll terminal can be the same ordifferent. For example, when the public transportation corresponding tothe public transportation charging service is metro, the station-exittoll terminal and the station-entry toll terminal can be differentterminals. When the public transportation corresponding to the publictransportation charging service is bus, the station-exit toll terminaland the station-entry toll terminal can be the same terminal.

In some embodiments, the data processing system can further include acharging server. The charging server can communicate with thestation-entry toll terminal and the station-exit toll terminal. Thecharging server can be a server, or a server cluster that includesmultiple servers.

In some embodiments, the data processing system can further include apayment server. The payment server can communicate with the mobileterminal. The payment server can be a server, or a server cluster thatincludes multiple servers.

Some embodiments of the present specification provide a data processingmethod. The data processing method is implemented by the data processingsystem.

In some embodiments, the mobile terminal can provide a service codemanagement interface. The mobile terminal can receive a specifiedquantity that is input by a user in the service code managementinterface; can generate the specified quantity of service codes; and candisplay the specified quantity of service codes. Specifically, thespecified quantity can be multiple. Each service code can include useridentification information. For example, the user identificationinformation can be a user account, a code of the user account, or anyother form of information that can be used to deduce the user account.For example, the user account can be an ALIPAY account, a WeChataccount, a bus card number, a metro card number, an all-in-one city cardnumber, etc. The user identification information included in thespecified quantity of service codes can be the same. Each service codecan represent one service order initiated by the mobile terminal. Eachservice code can include order identification information, and the orderidentification information can be used to identify a service orderrepresented by the service code. Order identification information indifferent service codes can be different.

In some embodiments, after arriving at the entry station, the user canuse a service code that has not been scanned and recognized by thestation-entry toll terminal for code scanning by the station-entry tollterminal at the entry station, so as to take public transportation atthe entry station. Considering that the mobile terminal can displaymultiple service codes, the user can perform code scanning multipletimes, so that multiple persons (for example, the user and the user'sparents, etc.) traveling together take public transportation at theentry station. A quantity of times the user scans the code can be lessthan or equal to the specified quantity. Each time the user scans aservice code, the station-entry toll terminal can obtain the servicecode through scanning; can identify the service code to obtain useridentification information and order identification information; and cansend the user identification information, the order identificationinformation, and entry station information to the charging server. Theentry station information can be used to identify the entry station, andcan be, for example, a name or a number of the entry station. Thecharging server can receive the user identification information, theorder identification information, and the entry station information, soas to charge a user account corresponding to the user identificationinformation.

In some embodiments, after arriving at the exit station, the user canuse the service code that has been scanned and recognized by thestation-entry toll terminal but has not been scanned and recognized bythe station-exit toll terminal for code scanning by the station-exittoll terminal at the exit station, so as to leave the exit station.Considering that multiple persons traveling together may not leave atthe same exit station, the user can perform code scanning once ormultiple times, so that one or more of the multiple persons travelingtogether leave the exit station. Each time the user scans a servicecode, the station-exit toll terminal can obtain the service code throughscanning; can identify the service code to obtain user identificationinformation and order identification information; and can send the useridentification information, the order identification information, andexit station information to the charging server. The exit stationinformation can be used to identify the exit station, and can be, forexample, a name or a number of the exit station. The charging server canreceive the user identification information, the order identificationinformation, and the exit station information; can determine a chargingamount based on the previously received entry station information thatcorresponds to both the user identification information and the orderidentification information, and a charging rule; and can send a paymentrequest to the payment server. The payment request can include the useridentification information, the order identification information, andthe charging amount. Certainly, the payment request can further includeother information, such as payee account information. The payment servercan receive the payment request; can deduct money from a user accountcorresponding to the user identification information based on thecharging amount; and can send payment result information to the mobileterminal. The payment result information can include the orderidentification information. Certainly, the payment result informationcan further include other information, such as the user identificationinformation and/or the charging amount.

Further references can be made to FIG. 1, FIG. 4, FIG. 5, FIG. 6, FIG.7, and FIG. 8. Some embodiments of the present specification furtherprovide another data processing method. The data processing method canbe performed by a mobile terminal. The data processing method caninclude the following steps.

Step S10: Provide a service code management interface.

In some embodiments, the service code management interface can beprovided by the mobile terminal for a user to set a quantity of servicecodes to be generated. The mobile terminal can display the service codemanagement interface after receiving an interface display instruction.

The interface display instruction can be automatically generated by themobile terminal. For example, the mobile terminal can run an applicationprogram. After the application program is started, the interface displayinstruction can be generated by default.

Alternatively, the interface display instruction can be generatedthrough triggering by a user operation. For example, the mobile terminalcan generate the interface display instruction after detecting that oneor any combination of multiple specified keys is pressed, tapped,double-tapped, or swiped. The specified key can be a virtual key or aphysical key. For example, references are made to FIG. 4, the virtualkey 402 can be a button control or a graphic control, etc. The physicalkey can be a press button, a rocker button, a dial, a slider switch, ora joystick, etc. For another example, the mobile terminal can furthergenerate the interface display instruction after recognizing apredetermined gesture. For example, the predetermined gesture can beswiping left, swiping right, etc. For another example, the mobileterminal can have a gyroscope and/or an acceleration sensor. The mobileterminal can further generate the interface display instruction afterdetecting a predetermined motion state by using a gyroscope and/or anacceleration sensor. For example, the predetermined motion state can beshaking, etc.

Step S12: Receive a specified quantity that is input by a user in theservice code management interface.

In some embodiments, the specified quantity can be a quantity of servicecodes to be generated by the mobile terminal. Specifically, thespecified quantity can be multiple, for example, two, three, or five.The mobile terminal can receive, in any method, the specified quantitythat is input by the user in the service code management interface. Forexample, references are made to FIG. 5, the service code managementinterface 502 can include a text box 504. The user can input thespecified quantity in the text box 504. The mobile terminal can receivethe specified quantity that is input by the user in the text box 504.For another example, the user can input first audio information in theservice code management interface. The mobile terminal can receive thefirst audio information that is input by the user; and can recognize thefirst audio information to obtain the specified quantity.

Step S14: Generate the specified quantity of service codes.

In some embodiments, for the description of the service code, referencescan be made to the previous embodiments. The mobile terminal cangenerate the specified quantity of service codes after receiving aservice code generation instruction. A process of generating the servicecode generation instruction can be similar to a process of generatingthe interface display instruction. The mobile terminal can generate thespecified quantity of service codes by using a service code generationalgorithm. Depending on different generated service codes, the servicecode generation algorithms can be the same or different. For example,when a two-dimensional code is generated, the service code generationalgorithm can be a quick response code (QR code) algorithm. A personskilled in the art should understand that, the QR code algorithm here isonly an example, and in fact any algorithm that can generate atwo-dimensional code can be applied here. Certainly, when other servicecodes are generated, the service code generation algorithm can also beother algorithms, which are not listed here one by one. In addition, themobile terminal can generate the specified quantity of service codesoffline. Alternatively, the mobile terminal can generate the specifiedquantity of service codes by interacting with a payment server online.For the description of the payment server, references can be made to theprevious embodiments.

Step S16: Display the specified quantity of service codes.

In some embodiments, the mobile terminal can display the specifiedquantity of service codes in any method. For example, references aremade to FIG. 6, the mobile terminal can provide a service code displayinterface 602; and can display the specified quantity of service codes604, 606, 608, 610 in the service code display interface 602.

References are made to FIG. 7, in some implementations of someembodiments, after receiving a first label generation instruction for afirst service code, the mobile terminal can generate a first label 702for the first service code; and can display the first label 702. Thefirst service code can include a service code that has been scanned andrecognized by the station-entry toll terminal but has not been scannedand recognized by the station-exit toll terminal. The first label 702can be used to indicate that a service order represented by the firstservice code is in a charging state. For example, the first label 702can be “entered”.

The first label generation instruction can be generated throughtriggering by a user operation. For example, the user can trigger theservice code that has been scanned and recognized by the station-entrytoll terminal but has not been scanned and recognized by thestation-exit toll terminal. After detecting the trigger operation, themobile terminal can use a service code corresponding to the triggeroperation as a first service code; and can generate a first labelgeneration instruction for the first service code. For example, thetrigger operation can include a tap operation, a double-tap operation, apress operation, a swipe operation, an operation of pressing and holdingfor more than a predetermined time (also referred to as a touch and holdoperation), etc.

Alternatively, the first label generation instruction can be generatedafter tolling start information sent by the payment server is received.Specifically, the user can use a service code that has not been scannedand recognized by the station-entry toll terminal for code scanning bythe station-entry toll terminal at the entry station. The station-entrytoll terminal can obtain the service code through scanning; can identifythe service code to obtain user identification information and orderidentification information; and can send the user identificationinformation, the order identification information, and entry stationinformation to the charging server. The charging server can receive theuser identification information, the order identification information,and the entry station information; and can send the tolling startinformation to the payment server. The tolling start information caninclude the order identification information. Certainly, the tollingstart information can further include other information, such as theuser identification information and/or the entry station information.The payment server can receive the tolling start information; and cansend the tolling start information to the mobile terminal. The mobileterminal can receive the tolling start information; can use a servicecode that includes the order identification information in the tollingstart information as a first service code; and can generate a firstlabel generation instruction for the first service code.

In some implementations of some embodiments, after receiving a secondlabel generation instruction for a second service code, the mobileterminal can generate a second label 704 for the second service code;and can display the second label 704. The second service code 704 caninclude a service code that has been scanned and recognized by thestation-exit toll terminal. The second label 704 can be used to indicatethat a service order represented by the second service code is in apayment end state. For example, the second label 704 can be “exited”.

The second label generation instruction can be generated throughtriggering by a user operation. For example, the user can trigger theservice code that has been scanned and recognized by the station-exittoll terminal. After detecting the trigger operation, the mobileterminal can use a service code corresponding to the trigger operationas a second service code; and can generate a second label generationinstruction for the second service code. For example, the triggeroperation can include a tap operation, a double-tap operation, a pressoperation, a swipe operation, an operation of pressing and holding formore than a predetermined time (also referred to as a touch and holdoperation), etc.

Alternatively, the second label generation instruction can be generatedafter payment result information sent by the payment server is received.Specifically, the user can use the service code that has been scannedand recognized by the station-entry toll terminal but has not beenscanned and recognized by the station-exit toll terminal for codescanning by the station-exit toll terminal at the exit station. Thestation-exit toll terminal can obtain the service code through scanning;can identify the service code to obtain user identification informationand order identification information; and can send the useridentification information, the order identification information, andexit station information to the charging server. The charging server canreceive the user identification information, the order identificationinformation, and the exit station information; can determine a chargingamount based on the previously received entry station information thatcorresponds to both the user identification information and the orderidentification information, and a charging rule; and can send a paymentrequest to the payment server. The payment request can include the useridentification information, the order identification information, andthe charging amount. The payment server can receive the payment request;can deduct money from a user account corresponding to the useridentification information based on the charging amount; and can sendpayment result information to the mobile terminal. The payment resultinformation can include the order identification information. The mobileterminal can receive the payment result information; can use a servicecode that includes the order identification information in the paymentresult information as a second service code; and can generate a secondlabel generation instruction for the second service code.

In some implementations of some embodiments, after receiving a thirdlabel generation instruction for a third service code, the mobileterminal can generate a third label 706 for the third service code; andcan display the third label 706. The third service code can include aservice code that has not been scanned and recognized by thestation-entry toll terminal. The third label 706 can be used to indicatethat a service order represented by the third service code is in acanceled state. For example, the third label 706 can be “canceled”.

The third label generation instruction can be generated throughtriggering by a user operation. For example, the user can trigger theservice code that has not been scanned and recognized by thestation-entry toll terminal. After detecting the trigger operation, themobile terminal can use a service code corresponding to the triggeroperation as a third service code; and can generate a third labelgeneration instruction for the third service code. For example, thetrigger operation can include a tap operation, a double-tap operation, apress operation, a swipe operation, an operation of pressing and holdingfor more than a predetermined time (also referred to as a touch and holdoperation), etc.

References are made to FIG. 8, in some implementations of someembodiments, after receiving an enlarged display instruction for afourth service code, the mobile terminal can enter an enlarged displayinterface 802 for enlarged display of the fourth service code 804. Inthe enlarged display interface, the fourth service code 804 is in anenlarged display state, facilitating code scanning by the user. Thefourth service code 804 can include a service code that has not beenscanned and recognized by the station-entry toll terminal, and a servicecode that has been scanned and recognized by the station-entry tollterminal but has not been scanned and recognized by the station-exittoll terminal.

The enlarged display instruction can be generated through triggering bya user operation. For example, the user can trigger the service codethat has not been scanned and recognized by the station-entry tollterminal. After detecting the trigger operation, the mobile terminal canuse a service code corresponding to the trigger operation as a fourthservice code; and can generate an enlarged display instruction for thefourth service code. For example, the trigger operation can include atap operation, a double-tap operation, a press operation, a swipeoperation, an operation of pressing and holding for more than apredetermined time (also referred to as a touch and hold operation),etc. For another example, the user can trigger the service code that hasbeen scanned and recognized by the station-entry toll terminal but hasnot been scanned and recognized by the station-exit toll terminal. Afterdetecting the trigger operation, the mobile terminal can use a servicecode corresponding to the trigger operation as a fourth service code;and can generate an enlarged display instruction for the fourth servicecode.

Alternatively, the enlarged display instruction can be generated aftersecond audio information is received. Specifically, as describedpreviously, the mobile terminal can display the specified quantity ofservice codes. At least one service code in the specified quantity ofservice codes can have a label. The label can include a first label, asecond label, a third label, etc. As such, the user can input the secondaudio information. The mobile terminal can receive audio informationthat is input by a user; can recognize the second audio information toobtain a target label; can use a service code that has the target labelas a fourth service code; and can generate an enlarged displayinstruction for the fourth service code. For example, the second audioinformation can be “display the service code that has been used forentry”, and then the target label can be the first label “entered”. Foranother example, the second audio information can be “display theservice code that has been used for exit”, and then the target label canbe the second label “exited”.

In some implementations of some embodiments, as described previously,the mobile terminal can display the specified quantity of service codes.At least one service code in the specified quantity of service codes canhave a label. The label can include a first label, a second label, athird label, etc. As such, after receiving a label broadcast instructionfor a fifth service code, the mobile terminal can broadcast a label thatthe fifth service code has. The fifth service code can include a servicecode that has been scanned and recognized by the station-entry tollterminal, but has not been scanned and recognized by the station-exittoll terminal, and a service code that has been scanned and recognizedby the station-exit toll terminal.

The label broadcast instruction can be generated through triggering by auser operation. For example, the user can trigger the service code thathas been scanned and recognized by the station-entry toll terminal buthas not been scanned and recognized by the station-exit toll terminal.After detecting the trigger operation, the mobile terminal can use aservice code corresponding to the trigger operation as a fifth servicecode; and can generate a label broadcast instruction for the fifthservice code. For another example, the user can trigger the service codethat has been scanned and recognized by the station-exit toll terminal.After detecting the trigger operation, the mobile terminal can use aservice code corresponding to the trigger operation as a fifth servicecode; and can generate a label broadcast instruction for the fifthservice code.

In some embodiments, the mobile terminal can provide the service codemanagement interface; can receive the specified quantity that is inputby the user in the service code management interface; can generate thespecified quantity of service codes, where the specified quantity ofservice codes include the same user identification information; and candisplay the specified quantity of service codes. As such, when multiplepersons traveling together take public transportation and one of themmakes payment, the user performs the operation once so that the mobileterminal generates multiple service codes, thereby simplifying useroperations and improving user experience.

References are made to FIG. 2. Some embodiments of the presentspecification provide a data processing apparatus. The data processingapparatus can include the following units: a providing unit 20,configured to provide a service code management interface; a receivingunit 22, configured to receive a specified quantity that is input by auser in the service code management interface; a generating unit 24,configured to generate the specified quantity of service codes, wherethe specified quantity of service codes include the same useridentification information; and a displaying unit 26, configured todisplay the specified quantity of service codes.

References are made to FIG. 3. Some embodiments of the presentspecification provide a terminal device 302. The terminal device caninclude a displaying component 304 and a processor 306.

In some embodiments, the displaying component 304 can include but is notlimited to a liquid crystal display (LCD), a cathode ray tube (CRT)display, a light emitting diode (LED) display, etc. The displayingcomponent 304 can be configured to display a service code managementinterface and a service code.

In some embodiments, the processor can be implemented in any propermethod. For example, the processor can take the form of, for example, amicroprocessor or processor, a computer-readable medium storing computerreadable program code (such as software or firmware) executable by themicroprocessor or processor, a logic gate, a switch, an applicationspecific integrated circuit (ASIC), a programmable logic controller, andan embedded microcontroller. The processor can be coupled to thedisplaying component, and configured to: control the displayingcomponent to display the service code management interface; receive aspecified quantity that is input by a user in the service codemanagement interface; generate the specified quantity of service codes,where the specified quantity of service codes include the same useridentification information; and control the displaying component todisplay the specified quantity of service codes.

Some embodiments of the present specification are described in aprogressive way. For same or similar parts of some embodiments, mutualreferences can be made to some embodiments. Each embodiment focuses on adifference from the other embodiments. Particularly, data processingapparatus embodiments and terminal device embodiments are basicallysimilar to method embodiments, and therefore are described briefly. Forrelated parts, references can be made to related descriptions in themethod embodiments.

In the 1990 s, whether a technical improvement is a hardware improvement(for example, an improvement to a circuit structure, such as a diode, atransistor, or a switch) or a software improvement (an improvement to amethod procedure) can be clearly distinguished. However, as technologiesdevelop, current improvements to many method procedures can beconsidered as direct improvements to hardware circuit structures. Adesigner usually programs an improved method procedure into a hardwarecircuit, to obtain a corresponding hardware circuit structure.Therefore, a method procedure can be improved by using a hardware entitymodule. For example, a programmable logic device (PLD) (for example, afield programmable gate array (FPGA)) is such an integrated circuit, anda logical function of the PLD is determined by a user through deviceprogramming. The designer performs programming to “integrate” a digitalsystem to a PLD without requesting a chip manufacturer to design andproduce an application-specific integrated circuit chip. In addition, atpresent, instead of manually manufacturing an integrated chip, this typeof programming is mostly implemented by using “logic compiler” software.The programming is similar to a software compiler used to develop andwrite a program. Original code needs to be written in a particularprogramming language for compilation. The language is referred to as ahardware description language (HDL). There are many HDLs, such as theAdvanced Boolean Expression Language (ABEL), the Altera HardwareDescription Language (AHDL), Confluence, the Cornell UniversityProgramming Language (CUPL), HDCal, the Java Hardware DescriptionLanguage (JHDL), Lava, Lola, MyHDL, PALASM, and the Ruby HardwareDescription Language (RHDL). The very-high-speed integrated circuithardware description language (VHDL) and Verilog2 are most commonlyused. A person skilled in the art should also understand that a hardwarecircuit that implements a logical method procedure can be readilyobtained once the method procedure is logically programmed by using thesome described hardware description languages and is programmed into anintegrated circuit.

The system, apparatus, module, or unit illustrated in the previousembodiments can be implemented by using a computer chip or an entity, orcan be implemented by using a product having a certain function. Atypical implementation device is a computer. Specifically, for example,the computer can be a personal computer, a laptop computer, a cellularphone, a camera phone, a smart phone, a personal digital assistant, amedia player, a navigation device, an e-mail device, a game console, atablet computer, a wearable device, or any combination of these devices.

It can be seen from the descriptions of the implementations that aperson skilled in the art can clearly understand that the presentspecification can be implemented by using software and a necessarygeneral hardware platform. Based on such an understanding, the technicalsolutions in the present specification essentially or the partcontributing to the existing technology can be implemented in a form ofa software product. The computer software product can be stored in astorage medium, such as a ROM/RAM, a magnetic disk, or an optical disc,and includes some instructions for instructing a computer device (can bea personal computer, a server, or a network device) to perform themethods described in some embodiments or in some parts of someembodiments of the present specification.

The present specification can be applied to many general-purpose orspecial-purpose computer system environments or configurations, forexample, a personal computer, a server computer, a handheld device or aportable device, a tablet device, a multi-processor system, amicroprocessor-based system, a set-top box, a programmable consumerelectronic device, a network PC, a minicomputer, a mainframe computer,and a distributed computing environment including any one of theprevious systems or devices.

The present specification can be described in the general context ofcomputer-executable instructions, for example, a program module.Generally, the program module includes a routine, a program, an object,a component, a data structure, etc. executing a specific task orimplementing a specific abstract data type. The present specificationcan also be practiced in distributed computing environments. In thedistributed computing environments, tasks are performed by remoteprocessing devices connected through a communications network. In adistributed computing environment, the program module can be located inboth local and remote computer storage media including storage devices.

Although the present specification is described by using someembodiments, a person of ordinary skill in the art knows that manyvariations of the present specification can be made without departingfrom the spirit of the present specification. It is expected that theappended claims include these variations without departing from thespirit of the present specification.

What is claimed is:
 1. A computer-implemented method, comprising:providing, by one or more processing devices, a service code managementinterface; receiving, by the one or more processing devices, a userinput specifying a quantity of a plurality of scannable service codes inthe service code management interface; generating, by the one or moreprocessing devices, the plurality of scannable service codes, whereinthe plurality of scannable service codes comprises a same useridentification information, wherein the same user identificationinformation comprises a user financial account; displaying, on a usermobile terminal, by the one or more processing devices, the plurality ofscannable service codes; determining, by the one or more processingdevices, that a first service code of the displayed plurality ofscannable service codes has been scanned by a transportationstation-entry toll terminal at an entry station; generating anddisplaying, by the one or more processing devices, a first label thatoverlays the displayed first service code and indicates that the firstservice code is in a first payment status, wherein the first paymentstatus comprises a payment opening status that indicates that the userfinancial account starts being charged; determining, by the one or moreprocessing devices, that a second service code of the displayedplurality of scannable service codes has been scanned by atransportation station-exit toll terminal at an exit station; andgenerating and displaying, by the one or more processing devices, asecond label that overlays the displayed second service code andindicates that the second service code is in a second payment status,wherein the second payment status comprises a payment end status thatindicates that a final payment amount is to be deducted from the userfinancial account.
 2. The computer-implemented method of claim 1,wherein each scannable service code further comprises orderidentification information, the first label is generated after tollingstart information is received, and the tolling start informationcomprises the order identification information in the first servicecode.
 3. The computer-implemented method of claim 1, wherein eachscannable service code further comprises order identificationinformation; the second label is generated after payment resultinformation is received; and the payment result information comprisesthe order identification information in the second service code.
 4. Thecomputer-implemented method of claim 1, further comprising: afterreceiving a third label generation instruction for a third service codeof the plurality of scannable service codes, generating a third labelfor the third service code, wherein the third label is used to indicatethat the third service code is in a canceled state; and displaying thethird label.
 5. The computer-implemented method of claim 1, furthercomprising: after receiving an enlarged display instruction for a fourthservice code of the plurality of scannable service codes, entering anenlarged display interface for enlarged display of the fourth servicecode.
 6. The computer-implemented method of claim 1, further comprising:after receiving a label broadcast instruction for a fifth service codeof the plurality of scannable service codes, broadcasting a labelassociated with the fifth service code.
 7. The computer-implementedmethod of claim 1, wherein each scannable service code further comprisesorder identification information; and the order identificationinformation in different scannable service codes is different.
 8. Anon-transitory, computer-readable medium storing one or moreinstructions executable by a computer system to perform operationscomprising: providing a service code management interface; receiving auser input specifying a quantity of a plurality of scannable servicecodes in the service code management interface; generating the pluralityof scannable service codes, wherein the plurality of scannable servicecodes comprises a same user identification information, wherein the sameuser identification information comprises a user financial account;displaying, on a user mobile terminal, the plurality of scannableservice codes; determining that a first service code of the displayedplurality of scannable service codes has been scanned by atransportation station-entry toll terminal at an entry station;generating and displaying a first label that overlays the displayedfirst service code and indicates that the first service code is in afirst payment status, wherein the first payment status comprises apayment opening status that indicates that the user financial accountstarts being charged; determining that a second service code of thedisplayed plurality of scannable service codes has been scanned by atransportation station-exit toll terminal at an exit station; andgenerating and displaying a second label that overlays the displayedsecond service code and indicates that the second service code is in asecond payment status, wherein the second payment status comprises apayment end status that indicates that a final payment amount is to bededucted from the user financial account.
 9. The non-transitory,computer-readable medium of claim 8, wherein each scannable service codefurther comprises order identification information, the first label isgenerated after tolling start information is received, and the tollingstart information comprises the order identification information in thefirst service code.
 10. The non-transitory, computer-readable medium ofclaim 8, wherein each scannable service code further comprises orderidentification information; the second label generation instruction isgenerated after payment result information is received; and the paymentresult information comprises the order identification information in thesecond service code.
 11. The non-transitory, computer-readable medium ofclaim 8, wherein the operations further comprise: after receiving athird label generation instruction for a third service code of theplurality of scannable service codes, generating a third label for thethird service code, wherein the third label is used to indicate that thethird service code is in a canceled state; and displaying the thirdlabel.
 12. The non-transitory, computer-readable medium of claim 8,wherein the operations further comprise: after receiving an enlargeddisplay instruction for a fourth service code of the plurality ofscannable service codes, entering an enlarged display interface forenlarged display of the fourth service code.
 13. The non-transitory,computer-readable medium of claim 8, wherein the operations furthercomprise: after receiving a label broadcast instruction for a fifthservice code of the plurality of scannable service codes, broadcasting alabel associated with the fifth service code.
 14. The non-transitory,computer-readable medium of claim 8, wherein each scannable service codefurther comprises order identification information; and the orderidentification information in different scannable service codes isdifferent.
 15. A computer-implemented system, comprising: one or morecomputers; and one or more computer memory devices interoperably coupledwith the one or more computers and having tangible, non-transitory,machine-readable media storing one or more instructions that, whenexecuted by the one or more computers, perform one or more operationscomprising: providing a service code management interface; receiving auser input specifying a quantity of a plurality of scannable servicecodes in the service code management interface; generating the pluralityof scannable service codes, wherein the plurality of scannable servicecodes comprises a same user identification information, wherein the sameuser identification information comprises a user financial account;displaying, on a user mobile terminal, the plurality of scannableservice codes; determining that a first service code of the displayedplurality of scannable service codes has been scanned by atransportation station-entry toll terminal at an entry station;generating and displaying a first label that overlays the displayedfirst service code and indicates that the first service code is in afirst payment status, wherein the first payment status comprises apayment opening status that indicates that the user financial accountstarts being charged; determining that a second service code of thedisplayed plurality of scannable service codes has been scanned by atransportation station-exit toll terminal at an exit station; andgenerating and displaying a second label that overlays the displayedsecond service code and indicates that the second service code is in asecond payment status, wherein the second payment status comprises apayment end status that indicates that a final payment amount is to bededucted from the user financial account.